Security News
Opengrep Emerges as Open Source Alternative Amid Semgrep Licensing Controversy
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
typescript-eslint
Advanced tools
typescript-eslint is a set of tools that allows you to use ESLint to lint TypeScript code. It provides a parser that can read TypeScript code and a set of rules that are specific to TypeScript, enabling you to enforce coding standards and catch potential issues in your TypeScript projects.
Linting TypeScript Code
This configuration file sets up ESLint to use the TypeScript parser and includes recommended rules from the @typescript-eslint plugin. It also adds a custom rule to error on unused variables.
module.exports = {
parser: '@typescript-eslint/parser',
plugins: ['@typescript-eslint'],
extends: [
'eslint:recommended',
'plugin:@typescript-eslint/recommended'
],
rules: {
'@typescript-eslint/no-unused-vars': 'error'
}
};
Type-Aware Rules
This configuration enables type-aware linting rules by specifying a TypeScript project. The rule '@typescript-eslint/no-floating-promises' ensures that promises are properly handled.
module.exports = {
parser: '@typescript-eslint/parser',
parserOptions: {
project: './tsconfig.json'
},
plugins: ['@typescript-eslint'],
extends: [
'plugin:@typescript-eslint/recommended-requiring-type-checking'
],
rules: {
'@typescript-eslint/no-floating-promises': 'error'
}
};
Custom Rules
This configuration enforces explicit return types on functions, but allows expressions to omit the return type. This helps in maintaining clear and predictable function signatures.
module.exports = {
parser: '@typescript-eslint/parser',
plugins: ['@typescript-eslint'],
rules: {
'@typescript-eslint/explicit-function-return-type': ['error', {
allowExpressions: true
}]
}
};
TSLint is an extensible static analysis tool that checks TypeScript code for readability, maintainability, and functionality errors. However, TSLint has been deprecated in favor of ESLint and typescript-eslint, as the latter provides a more flexible and extensible architecture.
ESLint is a widely-used linting tool for JavaScript. While it does not natively support TypeScript, it can be extended with the typescript-eslint parser and plugin to lint TypeScript code. This makes ESLint a versatile tool for projects that use both JavaScript and TypeScript.
Prettier is an opinionated code formatter that supports multiple languages, including TypeScript. While it is not a linter, it can be used alongside typescript-eslint to ensure consistent code formatting. Prettier focuses on code style, whereas typescript-eslint focuses on code quality and potential errors.
typescript-eslint
Tooling which enables you to use TypeScript with ESLint
š See https://typescript-eslint.io/packages/typescript-eslint for documentation on this package.
See https://typescript-eslint.io for general documentation on typescript-eslint, the tooling that allows you to run ESLint and Prettier on TypeScript code.
7.18.0 (2024-07-29)
You can read about our versioning strategy and releases on our website.
FAQs
Tooling which enables you to use TypeScript with ESLint
The npm package typescript-eslint receives a total of 3,945,611 weekly downloads. As such, typescript-eslint popularity was classified as popular.
We found that typescript-eslint demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.Ā It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.